@algesten I think it looks resonable. But this would not work if we had if a user brought their own RTP header extension?

@algesten I think it looks resonable. But this would not work if we had if a user brought their own RTP header extension?

What do you mean?

@algesten I think it looks resonable. But this would not work if we had if a user brought their own RTP header extension?

What do you mean?

  let mut pkt_ext_vals = ext_vals.clone();
            if !first {
                pkt_ext_vals.user_values.remove::<VideoLayersAllocation>();
            }

I read it as it will remove VideoLayesAllocation if it's not the first package.

If I create my own say DD header extension which should also only be on the first packet (similar to VLA)

I do not contribute this back to str0m, how can I avoid to get it attached to all packets in the frame?

@xnorpx the change only affected the Media level API, where it attaches the VLA while packetizing. With RTP-mode you can send anything you want on any packet.

@algesten yes, but I am talking about other header extensions on Media level API.

But we can just contribute those back and add in similar way to VLA (this is not a big blocker just pointing it out)

Thanks for merging!

@algesten @xnorpx, I can pull the list of extensions from libwebrtc that are not send in all packets and fix the behaviour here. For example, from a quick check, Absolute Capture Time is only sent on the first packet, Video Orientation is only sent on the last packet, and so on